MDL-based clustering for dependency mapping

ABSTRACT

Systems and methods are provided for automatically discovering applications/clusters in a network and mapping dependencies between the applications/clusters. A network monitoring system can capture network flow data using sensors executing on physical and/or virtual servers of the network and sensors executing on networking devices connected to the servers. The system can determine a graph including nodes, representing at least the servers, and edges, between pairs of the nodes of the graph indicating the network flow data includes one or more observed flows between pairs of the servers represented by the pairs of the nodes. The system can determine a dependency map, including representations of clusters of the servers and representations of dependencies between the clusters, based on the graph. The system can display a first representation of a first cluster of the dependency map and information indicating a confidence level of identifying the first cluster.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation of U.S. application Ser. No. 15/145,666, filed on May 3, 2016, which in turn, claims priority to U.S. Provisional Application 62/171,899, filed at Jun. 5, 2015, the disclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The subject matter of this disclosure relates in general to the field of computer networks, and more specifically for discovering applications and their interdependencies within a computer network.

BACKGROUND

An enterprise application is a set of workloads (e.g., computing, networking, and storage) that are generally distributed across various nodes (or endpoints) of a network and the relationships (e.g., connectivity, dependencies, network and security policies, etc.) between the workloads. A typical application may include a presentation tier, an application tier, and a data tier. The presentation tier may depend on the application tier and authentication services, and the application tier may depend on the web tier and external network services (e.g., a travel reservation system, an ordering tool, a billing tool, etc.). These tiers may further depend on firewall, load balancing, wide area network (WAN) acceleration, and other network services. An enterprise can include hundreds or thousands of applications of similar and different architectures.

An expansive or thorough understanding of a data center and applications running in the data center can be critical for network management tasks such as anomaly detection (e.g., network attacks and misconfiguration), asset management (e.g., monitoring, capacity planning, consolidation, migration, and continuity planning), and compliance (e.g. conformance with governmental regulations, industry standards, and corporate policies). Despite the complexities of the interrelationships among workloads discussed above, the traditional approaches for developing insight into an enterprise's workloads require comprehensive knowledge on the part of human operators and processes that are manual and largely customized for a particular enterprise. Automation of application dependency mapping (ADM) may be preferred because manual procedures often require a substantial degree of expertise yet may still be highly susceptible to error. Further, the evolving practices of modern data centers (e.g., virtualization, cloud computing, support for the Internet of Things (IoT), etc.), the increasing number and complexity of threats against networks, and new regulatory regimes that impose ever harsher penalties on non-compliant corporations demand new solutions for network management in the data center.

BRIEF DESCRIPTION OF THE FIGURES

In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example of a logical object model in accordance with an embodiment;

FIG. 2 illustrates an example of a network traffic monitoring system in accordance with an embodiment;

FIG. 3 illustrates an example of a network environment in accordance with an embodiment;

FIG. 4 illustrates an example of a data pipeline for determining clusters for application dependency mapping in accordance with an embodiment;

FIG. 5 illustrates an example of a graph for determining clusters for application dependency mapping in accordance with an embodiment;

FIG. 6 illustrates an example of a process for determining clusters for application dependency mapping in accordance with an embodiment; and

FIG. 7A and FIG. 7B illustrate examples of systems in accordance with some embodiments.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description of various configurations of embodiments and is not intended to represent the only configurations in which the subject matter of this disclosure can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject matter of this disclosure. However, it will be clear and apparent that the subject matter of this disclosure is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject matter of this disclosure.

Overview

A network can be configured to automate discovery of applications running in the network and map the applications' interdependencies. For example, the network can determine an optimum number of clusters for the network using the minimum description length (MDL) principle. The network can monitor network traffic and associated information (e.g., host information, process information, user information, etc.) passing through the network using a sensor network that provides multiple perspectives for the network traffic and associated information. The sensor network can include sensors for networking devices (e.g., routers, switches, network appliances), physical servers, hypervisors or shared kernels, and virtual partitions (e.g., VMs or containers), and other network elements. The network can analyze the network traffic and associated information to generate a graph. The nodes of the graph can include source endpoints, destination endpoints, and destination endpoint ports identified in the network traffic and associated information. The edges of the graph can include observed flows from the source endpoints to the destination endpoints at the destination ports. Each potential clustering can be evaluated according to an MDL score. The MDL score for a particular clustering can be based on description length values for each cluster combination of the clustering (e.g., source-destination-port combination). The description length value of a particular cluster combination can be based on a number of observed edges of the graph and unobserved edges of the graph corresponding to the cluster combination. The optimum number of clusters for the network may correspond to the number of clusters of the clustering associated with the minimum MDL score.

DESCRIPTION

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustrative purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without departing from the spirit and scope of the disclosure.

Network administrators often define and enforce policies to address network security, resource management, and other administrative functions. Conventional policies comprise of access control lists (ACLs) that establish whether certain types of traffic are allowed or denied by the network. A traditional implementation of policies involves their manual configuration using a device-centric model. For example, policies in such systems set forth rules that are to be applied to ports or IP addresses available on a host. Such an approach, however, runs a high risk of security breaches in the event of policy misconfiguration. In addition to the vulnerabilities exposed by human error, misconfiguration can also stem from lack of awareness regarding application context. For example, organizations may have tens of thousands to millions of access control lists (ACLs) and firewall rules. These organizations often lack the operational procedures to remove these policies in a timely manner when applications are decommissioned and/or these organizations prefer to retain policies that are no longer applicable because they are uncertain about the potential effect of removal.

Another common policy management scheme utilizes a virtualization-centric model, but systems relying on this design fail to address applications not running as virtual machines, containers, or other types of virtual partitions. Further, systems that enforce policy via hypervisors, shared kernels, or similar virtualization software require traffic pass through multiple policy enforcement points (e.g., source virtual machine or container, destination virtual machine or container, firewall, etc.). This routing can introduce additional overhead and opacity for inter-application connections.

Other conventional methods for administering policy rely on manual service chaining and a static network topology that is bound to network connections, VLAN, network interface, IP addressing, etc. This model requires policy configuration across multiple security devices (e.g., firewalls and intrusion detection and prevention systems (IDSs and IPSs)), slows application deployment, and scales poorly because applications are frequently created, moved, and decommissioned in the modern data center.

In some embodiments, a data center can implement an application-centric policy management model that facilitates seamless migration of applications and their corresponding policies, significantly reduces security risks, and ensures compliance in real time or substantially real time, among other features and benefits. FIG. 1 illustrates an example of a logical object model 100 for representing an application-centric policy management model in accordance with an embodiment. The policy management model 100 may utilize the concept of tenancy to allow for segregation of network infrastructure administration and traffic flow. Tenants 102 a, 102 b, . . . 102 n (collectively, “102”) can be logical containers or folders for applications 104 a, 104 b, . . . 104 f (collectively, “104”). The tenants can represent distinct customers (e.g., users of an infrastructure as a service (IaaS) provider), business units (e.g., human resources and sales), or other logical divisions (e.g., executives, employees, and contractors) depending on organizational needs. It will be appreciated that various configurations are possible. For example, an enterprise may be organized as one tenant for the entire organization, while a public cloud provider may have some customers represented as single tenants and other customers associated with multiple tenants.

The tenants 102 may be further broken down into private Layer 3 (L3) networks or contexts 106 a, 106 b, . . . 106 n (collectively, “106), which can map to Virtual Route Forwarding (VRF) instances or separate IP spaces. Each tenant 102 may have one or more private L3 networks or contexts 106 depending on their business needs. The private L3 networks or contexts 106 can provide each tenant 102 with a way to further separate its organizational and forwarding requirements. As the contexts 106 can use separate forwarding instances, IP addressing may be duplicated in separate contexts for the purpose of multitenancy.

In some embodiments, each “normal” tenant 102 can represent a unit of isolation from a policy perspective but may not necessarily represent a private network. For example, a “special” common tenant can have sharable policies that can be used by all of the tenants 102. The contexts 106, on the other hand, may represent private L3 namespaces or L3 networks, and can be units of isolation in the policy management model 100. Each tenant 102 can rely on several contexts 106. The contexts 106 can be instantiated by a tenant (i.e., contained by the tenant) or can be a part of a common tenant. This approach provides flexibility for networks by allowing both multiple private L3 networks per tenant and shared L3 networks used by multiple tenants.

Within each context 106 are objects called endpoint groups (EPGs) 108 a, 108 b, . . . 108 r (collectively, “108”) that define the applications 104. The EPGs 108 can be a collection of similar endpoints representing an application tier or set of services. The EPGs 108 are connected to each other via policies 110 a, 110 b, . . . 110 n (collectively, “110”) (labeled only for the application 102 c for clarity and simplicity). In the policy management model 100, the policies 100 can be more than just a set of ACLs and can include a collection of inbound/outbound filters, traffic quality settings, marking rules/redirection rules, and Layers 4-7 service device graphs.

The EPGs 108 are collections of one or more endpoints that provide a logical grouping for objects that require similar policy. For example, the EPGs 108 a, 108 b, and 108 c can be the group of components that respectively make up the web tier, application tier, and data tier of the application 108 a (e.g., a website or web service). Endpoints themselves can be defined using NIC, vNIC, IP address, or DNS name with extensibility for future methods of identifying application components. The EPGs 108 can also be used to represent other network elements such as external networks, network services, security devices, network storage, or other groupings. For example, an EPG can comprise endpoints connected to a virtual local area network (VLAN) or virtual extensible local area network (VXLAN), endpoints mapped to a port group, port profile, or other network virtualization grouping, endpoints corresponding to a set of IP addresses or subnets, endpoints corresponding to a set of domain names or domain name ranges, etc.

The use of the policy management model 100 can provide various advantages. The EPGs 108 can act as a single policy enforcement point for a group of network elements. This can simplify configuration of the policies 110 and ensure their consistency. Additional policy can be applied based on EPG rather than subnet as in conventional techniques. This means that IP addressing changes to an endpoint do not necessarily change the endpoint's policy, which is common in the case of conventional networks. In addition, moving an endpoint to another EPG can cause the switch, to which the endpoint is connected, to apply a new policy that defines new behavior for that endpoint based on the new EPG.

An additional benefit of the EPGs 108 relates to how policy may be enforced for an EPG. The physical ternary content-addressable memory (TCAM) in a switch, router, or other networking device where policy is stored for enforcement can be an expensive component of hardware and can therefore lower policy scale and/or raise hardware costs. Further, a policy table implemented in software using a conventional policy model may require more computing, storage, and network resources. Using the policy management model 100, policy can be applied via the hardware fabric (and/or software) based on EPG rather than on endpoint to substantially reduce the size of the TCAM/policy table. For example, the size of a set of policies stored in the TCAM/policy table can be represented as s×d×a, where ‘s’ is the number of sources, ‘d’ is the number of destinations, and ‘a’ is the number of network actions (e.g., forward, drop, mark for quality of service (QoS), etc.). In the policy management model 100, the sources ‘s’ and destinations ‘d’ become one entry for an EPG. On the other hand, if there are five sources, four destinations, and five network actions for a conventional network, the conventional TCAM/policy table would require 100 policy entries.

A related advantage of the policy management model 100 over traditional systems concerns how the policies 110 can be defined in each system, such as whether policies are based on blacklist rules or whitelist rules. In a blacklist system, traffic is permitted as a matter of course unless there is a policy that explicitly prohibits traffic between endpoints. A whitelist system, on the other hand, denies traffic between endpoints unless there is a policy that explicitly allows traffic. As will be appreciated by one of ordinary skill, a whitelist system in which the default behavior is to prohibit data flow is inherently more secure than a blacklist system in which the default behavior is to allow data flow. Due to the limitations of the size of conventional policy tables discussed above, conventional networks are generally limited to a blacklist system because, for typical enterprises, the set of connections between endpoints that must be allowed is likelier to exceed the set of known connections that must be explicitly denied. The policy management model 100 does not suffer from the same restrictions and can support both policies based on blacklist rules or, preferably, policies based on whitelist rules.

Although there are many favorable characteristics of the policy management model 100 (or a similar application-centric model) over conventional networks, network administrators of traditional systems may be reluctant to commit to such a migration. Data centers can be complicated ecosystems built up over long periods of time (e.g., 5-10 years) with very little documentation or oversight, and siloed network and application teams have often been given the freedom to operate according to different standards (to the extent any exist). Thus, there are few people—if any—in an organization who may have extensive or comprehensive knowledge of their network and the interdependencies between network elements. Further, as discussed, an enterprise's policy set may run into the thousands or even millions. The ramifications of modifying an existing policy, let alone a wholesale migration from one policy set to another, can be another significant deterrent. Yet change may be necessary in view of the dynamic nature of applications in the modern data center in which workloads can migrate from host to host within a private network (e.g., virtualization) or from a private cloud to a public cloud or vice versa (e.g., hybrid cloud computing). In addition, manual processes may no longer be feasible in view of the vastness and complexities of modern networks. Systems and approaches in accordance with various embodiments may ease the frictions of migrating to an application-centric policy management model or facilitate building a data center from the ground up using the policy management model 100 or a similar model.

In some embodiments, application dependency mapping (ADM) can be substantially automated or entirely automated by observing data center traffic for a specified period of time. The traffic data can be collected from multiple perspectives to develop a more thorough data set from which to discover applications and their dependencies. The traffic data can be captured and processed in real time or substantially real time to accurately map endpoints to applications even when the endpoints migrate from host to host due to virtualization and/or cloud computing. The collected data can be evaluated using machine learning to determine an accurate and complete (or nearly complete) ADM. A set of policies, such as those based on whitelist rules, can be derived from the ADM. The policies can be simulated against historical ground truth traffic data and/or real time (or substantially real time) ground truth traffic data to determine their efficacy prior to implementing them in a production environment.

Conventional automated solutions, to the extent they exist, are traditionally limited to packet data captured by networking devices. In some embodiments, networks can be configured with sensors at multiple points, including on networking devices (e.g., switches, routers, gateways, firewalls, deep packet inspectors, traffic monitors, load balancers, etc.), physical servers, hypervisors or shared kernels, virtual partitions (e.g., VMs or containers), and other network elements. This can provide a more comprehensive view of the network. Further, network traffic data (e.g., flows) can be associated with host and/or endpoint data (e.g., host/endpoint name, operating system, CPU usage, network usage, disk space, logged users, scheduled jobs, open files, information regarding files stored on a host/endpoint, etc.), process data (e.g., process name, ID, parent process ID, path, CPU utilization, memory utilization, etc.), user data (e.g., user name, ID, login time, etc.), and other collectible data to provide more insight into network activity.

Conventional approaches may also be limited to networks with stationary nodes. As discussed, this is unworkable in modern data centers which may migrate virtual partitions (e.g., VMs or containers) from host to host both internally (i.e., within the data center) and externally (i.e., to and from a public cloud) in the event of a network or server failure or to balance workloads in the data center. In some embodiments, a data center captures network traffic data and associated host, process, and/or user data in real time or substantially real time and analyzes the captured network data to determine an up-to-date application topology.

An integral task of application dependency mapping is clustering or identifying endpoints performing similar workloads, communicating with a similar set of endpoints or networking devices, having similar network and security limitations (i.e., policies), and sharing other attributes. One of the difficulties of automating ADM is determining the optimal number of clusters and clustering in a network. If the number of clusters is too low and/or the clustering too broad, policies derived from such a clustering may be too “loose” and allow more communications between nodes than would be preferred. On the other hand, if there are too many clusters and/or too many narrowly defined clusters, policies generated from “excessive” clustering may be too costly to implement in hardware and/or software. Further, certain valid communications may be denied if the date/time range of the traffic data analyzed does not include instances of the valid communications.

In some embodiments, the minimum description length (MDL) principle can be utilized to determine the optimal number of clusters in a network. Under the MDL principle, the optimal theory or model for a body of data is the one that minimizes the size of the theory and the amount of information necessary to specify the exceptions relative to the theory. MDL posits that any regularity in the data can be used to compress (i.e., to describe it using fewer symbols than the number of symbols needed to describe the data literally) the data. Thus, the more regularities there are in the data, the more the data can be compressed. In MDL, learning is equivalent to finding regularity; the more that the data can be compressed, the more is learned about the data.

In some embodiments, potential clusterings can be compared to a communication graph comprising graph nodes (e.g., clients, servers, and server ports) and graph edges corresponding to observed flows that can be evaluated according to an MDL score to determine the optimal number of clusters. The MDL score for a particular clustering can be based on the sum of the description lengths for each cluster combination of the clustering (e.g., a source cluster—destination cluster—destination port combination). In some embodiments, the description length can be a function of the minimum between observed graph edges (i.e., collected traffic data includes data flows from a source cluster to a destination cluster at a port cluster) and unobserved graph edges (i.e., collected traffic data does not include data flows from a source cluster to a destination cluster at a port cluster).

In some embodiments, a network may comprise multiple partitions (e.g., based on routing information, subnet masks, or regions and zones), and clusters may not span the multiple partitions (i.e., a cluster may not include endpoints that are located in different partitions). Thus, the optimal clustering may vary from one partition to another in networks with multiple partitions. In some embodiments, the MDL principle can be used to improve the number of clusters for each individual partition by using a randomized local search algorithm based upon local searches.

FIG. 2 is an illustration of a network traffic monitoring system 200 in accordance with an embodiment. In some embodiments, the network traffic monitoring system 200 can be used to implement a policy management model, such as the policy management model 100 of FIG. 1, and to determine an optimal clustering based on MDL. The network traffic monitoring system 200 can include a configuration manager 202, sensors 204, a collector module 206, a data mover module 208, an analytics engine 210, and a presentation module 212. In FIG. 2, the analytics engine 210 is also shown in communication with out-of-band data sources 214, third party data sources 216, and a network controller 218.

The configuration manager 202 can be used to provision and maintain the sensors 204, including installing sensor software or firmware in various nodes of a network, configuring the sensors 204, updating the sensor software or firmware, among other sensor management tasks. For example, the sensors 204 can be implemented as virtual partition images (e.g., virtual machine (VM) images or container images), and the configuration manager 202 can distribute the images to host machines. In general, a virtual partition may be an instance of a VM, container, sandbox, or other isolated software environment. The software environment may include an operating system and application software. For software running within a virtual partition, the virtual partition may appear to be, for example, one of many servers or one of many operating systems executed on a single physical server. The configuration manager 202 can instantiate a new virtual partition or migrate an existing partition to a different physical server. The configuration manager 202 can also be used to configure the new or migrated sensor.

The configuration manager 202 can also monitor the health of the sensors 204. For example, the configuration manager 202 may request for status updates and/or receive heartbeat messages, initiate performance tests, generate health checks, and perform other health monitoring tasks. In some embodiments, the configuration manager 202 can also authenticate the sensors 204. For instance, the sensors 204 can be assigned a unique identifier, such as by using a one-way hash function of a sensor's basic input/out system (BIOS) universally unique identifier (UUID) and a secret key stored by the configuration image manager 202. The UUID can be a large number that may be difficult for a malicious sensor or other device or component to guess. In some embodiments, the configuration manager 202 can keep the sensors 204 up to date by installing the latest versions of sensor software and/or applying patches. The configuration manager 202 can obtain these updates automatically from a local source or the Internet.

The sensors 204 can reside on various nodes of a network, such as a virtual partition (e.g., VM or container) 220; a hypervisor or shared kernel managing one or more virtual partitions and/or physical servers 222, an application-specific integrated circuit (ASIC) 224 of a switch, router, gateway, or other networking device, or a packet capture (pcap) 226 appliance (e.g., a standalone packet monitor, a device connected to a network devices monitoring port, a device connected in series along a main trunk of a datacenter, or similar device), or other element of a network. The sensors 204 can monitor network traffic between nodes, and send network traffic data and corresponding data (e.g., host data, process data, user data, etc.) to the collectors 208 for storage. For example, the sensors 204 can sniff packets being sent over its hosts' physical or virtual network interface card (NIC) and/or individual processes can be configured to report network traffic and corresponding data to the sensors 204. Incorporating the sensors 204 on multiple nodes and within multiple partitions of some nodes of the network can provide for robust capture of network traffic and corresponding data. In some embodiments, each node of the network (e.g., VM, container, or other virtual partition 220, hypervisor, shared kernel, or physical server 222, ASIC 224, pcap 226, etc.) includes a respective sensor 204. However, it should be understood that various software and hardware configurations can be used to implement the sensor network 204.

As the sensors 204 capture communications and corresponding data, they may continuously send network traffic and corresponding data to the collectors 208. The network traffic data can include metadata relating to a packet, a collection of packets, a flow, a bidirectional flow, a group of flows, a session, or a network communication of another granularity. That is, the network traffic data can generally include any information describing communication on all layers of the Open Systems Interconnection (OSI) model. For example, the network traffic data can include source/destination MAC address, source/destination IP address, protocol, port number, etc. In some embodiments, the network traffic data can also include summaries of network activity or other network statistics such as number of packets, number of bytes, number of flows, bandwidth usage, response time, latency, packet loss, jitter, and other network statistics.

The sensors 204 can also determine additional data for each session, bidirectional flow, flow, packet, or other more granular or less granular network communication. The additional data can include host and/or endpoint information, virtual partition information, sensor information, process information, user information, tenant information, application information, network topology, application dependency mapping, cluster information, or other information corresponding to each flow.

In some embodiments, the sensors 204 can perform some preprocessing of the network traffic and corresponding data before sending the data to the collectors 208. For example, the sensors 204 can remove extraneous or duplicative data or they can create summaries of the data (e.g., latency, number of packets per flow, number of bytes per flow, number of flows, etc.). In some embodiments, the sensors 204 can be configured to only capture certain types of information and disregard the rest. In some embodiments, the sensors 204 can be configured to capture only a representative sample of packets (e.g., every 1,000th packet or other suitable sample rate) and corresponding data.

Since the sensors 204 may be located throughout the network, network traffic and corresponding data can be collected from multiple vantage points or multiple perspectives in the network to provide a more comprehensive view of network behavior. The capture of network traffic and corresponding data from multiple perspectives rather than just at a single sensor located in the data path or in communication with a component in the data path, allows the data to be correlated from the various data sources, which may be used as additional data points by the analytics engine 210. Further, collecting network traffic and corresponding data from multiple points of view ensures more accurate data is captured. For example, a conventional sensor network may be limited to sensors running on external-facing network devices (e.g., routers, switches, network appliances, etc.) such that east-west traffic, including VM-to-VM or container-to-container traffic on a same host, may not be monitored. In addition, packets that are dropped before traversing a network device or packets containing errors may not be accurately monitored by the conventional sensor network. The sensor network 204 of various embodiments substantially mitigates or eliminates these issues altogether by locating sensors at multiple points of potential failure. Moreover, the network traffic monitoring system 200 can verify multiple instances of data for a flow (e.g., source endpoint flow data, network device flow data, and endpoint flow data) against one another.

In some embodiments, the network traffic monitoring system 200 can assess a degree of accuracy of flow data sets from multiple sensors and utilize a flow data set from a single sensor determined to be the most accurate and/or complete. The degree of accuracy can be based on factors such as network topology (e.g., a sensor closer to the source may be more likely to be more accurate than a sensor closer to the destination), a state of a sensor or a node hosting the sensor (e.g., a compromised sensor/node may have less accurate flow data than an uncompromised sensor/node), or flow data volume (e.g., a sensor capturing a greater number of packets for a flow may be more accurate than a sensor capturing a smaller number of packets).

In some embodiments, the network traffic monitoring system 200 can assemble the most accurate flow data set and corresponding data from multiple sensors. For instance, a first sensor along a data path may capture data for a first packet of a flow but may be missing data for a second packet of the flow while the situation is reversed for a second sensor along the data path. The network traffic monitoring system 200 can assemble data for the flow from the first packet captured by the first sensor and the second packet captured by the second sensor.

As discussed, the sensors 204 can send network traffic and corresponding data to the collectors 206. In some embodiments, each sensor can be assigned to a primary collector and a secondary collector as part of a high availability scheme. If the primary collector fails or communications between the sensor and the primary collector are not otherwise possible, a sensor can send its network traffic and corresponding data to the secondary collector. In other embodiments, the sensors 204 are not assigned specific collectors but the network traffic monitoring system 200 can determine an optimal collector for receiving the network traffic and corresponding data through a discovery process. In such embodiments, a sensor can change where it sends it network traffic and corresponding data if its environments changes, such as if a default collector fails or if the sensor is migrated to a new location and it would be optimal for the sensor to send its data to a different collector. For example, it may be preferable for the sensor to send its network traffic and corresponding data on a particular path and/or to a particular collector based on latency, shortest path, monetary cost (e.g., using private resources versus a public resources provided by a public cloud provider), error rate, or some combination of these factors. In other embodiments, a sensor can send different types of network traffic and corresponding data to different collectors. For example, the sensor can send network traffic and corresponding data related to one type of process to one collector and network traffic and corresponding data related to another type of process to another collector.

The collectors 206 can be any type of storage medium that can serve as a repository for the network traffic and corresponding data captured by the sensors 204. In some embodiments, data storage for the collectors 206 is located in an in-memory database, such as dashDB from IBM®, although it should be appreciated that the data storage for the collectors 206 can be any software and/or hardware capable of providing rapid random access speeds typically used for analytics software. In various embodiments, the collectors 206 can utilize solid state drives, disk drives, magnetic tape drives, or a combination of the foregoing according to cost, responsiveness, and size requirements. Further, the collectors 206 can utilize various database structures such as a normalized relational database or a NoSQL database, among others.

In some embodiments, the collectors 206 may only serve as network storage for the network traffic monitoring system 200. In such embodiments, the network traffic monitoring system 200 can include a data mover module 208 for retrieving data from the collectors 206 and making the data available to network clients, such as the components of the analytics engine 210. In effect, the data mover module 208 can serve as a gateway for presenting network-attached storage to the network clients. In other embodiments, the collectors 206 can perform additional functions, such as organizing, summarizing, and preprocessing data. For example, the collectors 206 can tabulate how often packets of certain sizes or types are transmitted from different nodes of the network. The collectors 206 can also characterize the traffic flows going to and from various nodes. In some embodiments, the collectors 206 can match packets based on sequence numbers, thus identifying traffic flows and connection links. As it may be inefficient to retain all data indefinitely in certain circumstances, in some embodiments, the collectors 206 can periodically replace detailed network traffic and corresponding data with consolidated summaries. In this manner, the collectors 206 can retain a complete dataset describing one period (e.g., the past minute or other suitable period of time), with a smaller dataset of another period (e.g., the previous 2-10 minutes or other suitable period of time), and progressively consolidate network traffic and corresponding data of other periods of time (e.g., day, week, month, year, etc.). In some embodiments, network traffic and corresponding data for a set of flows identified as normal or routine can be winnowed at an earlier period of time while a more complete data set may be retained for a lengthier period of time for another set of flows identified as anomalous or as an attack.

Computer networks may be exposed to a variety of different attacks that expose vulnerabilities of computer systems in order to compromise their security. Some network traffic may be associated with malicious programs or devices. The analytics engine 210 may be provided with examples of network states corresponding to an attack and network states corresponding to normal operation. The analytics engine 210 can then analyze network traffic and corresponding data to recognize when the network is under attack. In some embodiments, the network may operate within a trusted environment for a period of time so that the analytics engine 210 can establish a baseline of normal operation. Since malware is constantly evolving and changing, machine learning may be used to dynamically update models for identifying malicious traffic patterns.

In some embodiments, the analytics engine 210 may be used to identify observations which differ from other examples in a dataset. For example, if a training set of example data with known outlier labels exists, supervised anomaly detection techniques may be used. Supervised anomaly detection techniques utilize data sets that have been labeled as normal and abnormal and train a classifier. In a case in which it is unknown whether examples in the training data are outliers, unsupervised anomaly techniques may be used. Unsupervised anomaly detection techniques may be used to detect anomalies in an unlabeled test data set under the assumption that the majority of instances in the data set are normal by looking for instances that seem to fit to the remainder of the data set.

The analytics engine 210 can include a data lake 230, an application dependency mapping (ADM) module 240, and elastic processing engines 250. The data lake 230 is a large-scale storage repository that provides massive storage for various types of data, enormous processing power, and the ability to handle nearly limitless concurrent tasks or jobs. In some embodiments, the data lake 230 is implemented using the Hadoop® Distributed File System (HDFS™) from Apache® Software Foundation of Forest Hill, Md. HDFS™ is a highly scalable and distributed file system that can scale to thousands of cluster nodes, millions of files, and petabytes of data. HDFS™ is optimized for batch processing where data locations are exposed to allow computations to take place where the data resides. HDFS™ provides a single namespace for an entire cluster to allow for data coherency in a write-once, read-many access model. That is, clients can only append to existing files in the node. In HDFS™, files are separated into blocks, which are typically 64 MB in size and are replicated in multiple data nodes. Clients access data directly from data nodes.

In some embodiments, the data mover 208 receives raw network traffic and corresponding data from the collectors 206 and distributes or pushes the data to the data lake 230. The data lake 230 can also receive and store out-of-band data 214, such as statuses on power levels, network availability, server performance, temperature conditions, cage door positions, and other data from internal sources, and third party data 216, such as security reports (e.g., provided by Cisco® Systems, Inc. of San Jose, Calif., Arbor Networks® of Burlington, Mass., Symantec® Corp. of Sunnyvale, Calif., Sophos® Group plc of Abingdon, England, Microsoft® Corp. of Seattle, Wash., Verizon® Communications, Inc. of New York, N.Y., among others), geolocation data, IP watch lists, Whois data, configuration management database (CMDB) or configuration management system (CMS) as a service, and other data from external sources. In other embodiments, the data lake 230 may instead fetch or pull raw traffic and corresponding data from the collectors 206 and relevant data from the out-of-band data sources 214 and the third party data sources 216. In yet other embodiments, the functionality of the collectors 206, the data mover 208, the out-of-band data sources 214, the third party data sources 216, and the data lake 230 can be combined. Various combinations and configurations are possible as would be known to one of ordinary skill in the art.

Each component of the data lake 230 can perform certain processing of the raw network traffic data and/or other data (e.g., host data, process data, user data, out-of-band data, third party data, etc.) to transform the raw data to a form useable by the elastic processing engines 250. In some embodiments, the data lake 230 can include repositories for flow attributes 232, host and/or endpoint attributes 234, process attributes 236, and policy attributes 238. In some embodiments, the data lake 230 can also include repositories for VM or container attributes, application attributes, tenant attributes, network topology, application dependency maps, cluster attributes, etc.

The flow attributes 232 relate to information about flows traversing the network. A flow is generally one or more packets sharing certain attributes that are sent within a network within a specified period of time. The flow attributes 232 can include packet header fields such as a source address (e.g., Internet Protocol (IP) address, Media Access Control (MAC) address, Domain Name System (DNS) name, or other network address), source port, destination address, destination port, protocol type, class of service, among other fields. The source address may correspond to a first endpoint (e.g., network device, physical server, virtual partition, etc.) of the network, and the destination address may correspond to a second endpoint, a multicast group, or a broadcast domain. The flow attributes 232 can also include aggregate packet data such as flow start time, flow end time, number of packets for a flow, number of bytes for a flow, the union of TCP flags for a flow, among other flow data.

The host and/or endpoint attributes 234 describe host and/or endpoint data for each flow, and can include host and/or endpoint name, network address, operating system, CPU usage, network usage, disk space, ports, logged users, scheduled jobs, open files, and information regarding files and/or directories stored on a host and/or endpoint (e.g., presence, absence, or modifications of log files, configuration files, device special files, or protected electronic information). As discussed, in some embodiments, the host and/or endpoints attributes 234 can also include the out-of-band data 214 regarding hosts such as power level, temperature, and physical location (e.g., room, row, rack, cage door position, etc.) or the third party data 216 such as whether a host and/or endpoint is on an IP watch list or otherwise associated with a security threat, Whois data, or geocoordinates. In some embodiments, the out-of-band data 214 and the third party data 216 may be associated by process, user, flow, or other more granular or less granular network element or network communication.

The process attributes 236 relate to process data corresponding to each flow, and can include process name (e.g., bash, httpd, netstat, etc.), ID, parent process ID, path (e.g., /usr2/username/bin/, /usr/local/bin, /usr/bin, etc.), CPU utilization, memory utilization, memory address, scheduling information, nice value, flags, priority, status, start time, terminal type, CPU time taken by the process, the command that started the process, and information regarding a process owner (e.g., user name, ID, user's real name, e-mail address, user's groups, terminal information, login time, expiration date of login, idle time, and information regarding files and/or directories of the user).

The policy attributes 238 contain information relating to network policies. As discussed, policies can dictate whether a particular flow is allowed or denied by the network as well as a specific route by which a packet traverses the network. For example, policies can be used to mark packets so that certain kinds of traffic receive differentiated service when used in combination with queuing techniques such as those based on priority, fairness, weighted fairness, token bucket, random early detection, round robin, among others. The policy attributes 238 can include policy statistics such as a number of times a policy was enforced or a number of times a policy was not enforced. The policy attributes 238 can also include associations with network traffic data. For example, flows found to be non-conformant can be linked or tagged with corresponding policies to assist in the investigation of non-conformance.

The analytics engine 210 may include any number of engines 250, including for example, a flow engine 252 for identifying flows (e.g., flow engine 252) or an attacks engine 254 for identify attacks to the network. In some embodiments, the analytics engine can include a separate distributed denial of service (DDoS) attack engine 255 for specifically detecting DDoS attacks. In other embodiments, a DDoS attack engine may be a component or a sub-engine of a general attacks engine. In some embodiments, the attacks engine 254 and/or the DDoS engine 255 can use machine learning techniques to identify security threats to a network. For example, the attacks engine 254 and/or the DDoS engine 255 can be provided with examples of network states corresponding to an attack and network states corresponding to normal operation. The attacks engine 254 and/or the DDoS engine 255 can then analyze network traffic data to recognize when the network is under attack. In some embodiments, the network can operate within a trusted environment for a time to establish a baseline for normal network operation for the attacks engine 254 and/or the DDoS.

The analytics engine 210 may further include a search engine 256. The search engine 256 may be configured, for example to perform a structured search, an NLP (Natural Language Processing) search, or a visual search. Data may be provided to the engines from one or more processing components.

The analytics engine 210 can also include a policy engine 258 that manages network policy, including creating and/or importing policies, monitoring policy conformance and non-conformance, enforcing policy, simulating changes to policy or network elements affecting policy, among other policy-related tasks.

The ADM module 240 can determine dependencies of applications of the network. That is, particular patterns of traffic may correspond to an application, and the interconnectivity or dependencies of the application can be mapped to generate a graph for the application (i.e., an application dependency mapping). In this context, an application refers to a set of networking components that provides connectivity for a given set of workloads. For example, in a conventional three-tier architecture for a web application, first endpoints of the web tier, second endpoints of the application tier, and third endpoints of the data tier make up the web application. The ADM module 240 can receive input data from various repositories of the data lake 230 (e.g., the flow attributes 232, the host and/or endpoint attributes 234, the process attributes 236, etc.). The ADM module 240 may analyze the input data to determine that there is first traffic flowing between external endpoints on port 80 of the first endpoints corresponding to Hypertext Transfer Protocol (HTTP) requests and responses. The input data may also indicate second traffic between first ports of the first endpoints and second ports of the second endpoints corresponding to application server requests and responses and third traffic flowing between third ports of the second endpoints and fourth ports of the third endpoints corresponding to database requests and responses. The ADM module 240 may define an ADM for the web application as a three-tier application including a first EPG comprising the first endpoints, a second EPG comprising the second endpoints, and a third EPG comprising the third endpoints.

The presentation module 216 can include an application programming interface (API) or command line interface (CLI) 260, a security information and event management (SIEM) interface 262, and a web front-end 264. As the analytics engine 210 processes network traffic and corresponding data and generates analytics data, the analytics data may not be in a human-readable form or it may be too voluminous for a user to navigate. The presentation module 216 can take the analytics data generated by analytics engine 210 and further summarize, filter, and organize the analytics data as well as create intuitive presentations for the analytics data.

In some embodiments, the API or CLI 260 can be implemented using Hadoop® Hive from Apache® for the back end, and Java® Database Connectivity (JDBC) from Oracle® Corporation of Redwood Shores, Calif., as an API layer. Hive is a data warehouse infrastructure that provides data summarization and ad hoc querying. Hive provides a mechanism to query data using a variation of structured query language (SQL) that is called HiveQL. JDBC is an application programming interface (API) for the programming language Java®, which defines how a client may access a database.

In some embodiments, the SIEM interface 262 can be implemented using Hadoop® Kafka for the back end, and software provided by Splunk®, Inc. of San Francisco, Calif. as the SIEM platform. Kafka is a distributed messaging system that is partitioned and replicated. Kafka uses the concept of topics. Topics are feeds of messages in specific categories. In some embodiments, Kafka can take raw packet captures and telemetry information from the data mover 208 as input, and output messages to a SIEM platform, such as Splunk®. The Splunk® platform is utilized for searching, monitoring, and analyzing machine-generated data.

In some embodiments, the web front-end 264 can be implemented using software provided by MongoDB®, Inc. of New York, N.Y. and Hadoop® ElasticSearch from Apache® for the back-end, and Ruby on Rails™ as the web application framework. MongoDB® is a document-oriented NoSQL database based on documents in the form of JavaScript® Object Notation (JSON) with dynamic schemas. ElasticSearch is a scalable and real time search and analytics engine that provides domain-specific language (DSL) full querying based on JSON. Ruby on Rails™ is model-view-controller (MVC) framework that provides default structures for a database, a web service, and web pages. Ruby on Rails™ relies on web standards such as JSON or extensible markup language (XML) for data transfer, and hypertext markup language (HTML), cascading style sheets, (CSS), and JavaScript® for display and user interfacing.

Although FIG. 2 illustrates an example configuration of the various components of a network traffic monitoring system, those of skill in the art will understand that the components of the network traffic monitoring system 200 or any system described herein can be configured in a number of different ways and can include any other type and number of components. For example, the sensors 204, the collectors 206, the data mover 208, and the data lake 230 can belong to one hardware and/or software module or multiple separate modules. Other modules can also be combined into fewer components and/or further divided into more components.

FIG. 3 illustrates an example of a network environment 300 in accordance with an embodiment. In some embodiments, a network traffic monitoring system, such as the network traffic monitoring system 200 of FIG. 2, can be implemented in the network environment 300. It should be understood that, for the network environment 300 and any environment discussed herein, there can be additional or fewer nodes, devices, links, networks, or components in similar or alternative configurations. Embodiments with different numbers and/or types of clients, networks, nodes, cloud components, servers, software components, devices, virtual or physical resources, configurations, topologies, services, appliances, deployments, or network devices are also contemplated herein. Further, the network environment 300 can include any number or type of resources, which can be accessed and utilized by clients or tenants. The illustrations and examples provided herein are for clarity and simplicity.

The network environment 300 can include a network fabric 302, a Layer 2 (L2) network 304, a Layer 3 (L3) network 306, and servers 308 a, 308 b, 308 c, 308 d, and 308 e (collectively, 308). The network fabric 302 can include spine switches 310 a, 310 b, 310 c, and 310 d (collectively, “310”) and leaf switches 312 a, 312 b, 312 c, 312 d, and 312 e (collectively, “312”). The spine switches 310 can connect to the leaf switches 312 in the network fabric 302. The leaf switches 312 can include access ports (or non-fabric ports) and fabric ports. The fabric ports can provide uplinks to the spine switches 310, while the access ports can provide connectivity to endpoints (e.g., the servers 308), internal networks (e.g., the L2 network 304), or external networks (e.g., the L3 network 306).

The leaf switches 312 can reside at the edge of the network fabric 302, and can thus represent the physical network edge. For instance, in some embodiments, the leaf switches 312 d and 312 e operate as border leaf switches in communication with edge devices 314 located in the external network 306. The border leaf switches 312 d and 312 e may be used to connect any type of external network device, service (e.g., firewall, deep packet inspector, traffic monitor, load balancer, etc.), or network (e.g., the L3 network 306) to the fabric 302.

Although the network fabric 302 is illustrated and described herein as an example leaf-spine architecture, one of ordinary skill in the art will readily recognize that various embodiments can be implemented based on any network topology, including any data center or cloud network fabric. Indeed, other architectures, designs, infrastructures, and variations are contemplated herein. For example, the principles disclosed herein are applicable to topologies including three-tier (including core, aggregation, and access levels), fat tree, mesh, bus, hub and spoke, etc. Thus, in some embodiments, the leaf switches 312 can be top-of-rack switches configured according to a top-of-rack architecture. In other embodiments, the leaf switches 312 can be aggregation switches in any particular topology, such as end-of-row or middle-of-row topologies. In some embodiments, the leaf switches 312 can also be implemented using aggregation switches.

Moreover, the topology illustrated in FIG. 3 and described herein is readily scalable and may accommodate a large number of components, as well as more complicated arrangements and configurations. For example, the network may include any number of fabrics 302, which may be geographically dispersed or located in the same geographic area. Thus, network nodes may be used in any suitable network topology, which may include any number of servers, virtual machines or containers, switches, routers, appliances, controllers, gateways, or other nodes interconnected to form a large and complex network. Nodes may be coupled to other nodes or networks through one or more interfaces employing any suitable wired or wireless connection, which provides a viable pathway for electronic communications.

Network communications in the network fabric 302 can flow through the leaf switches 312. In some embodiments, the leaf switches 312 can provide endpoints (e.g., the servers 308), internal networks (e.g., the L2 network 304), or external networks (e.g., the L3 network 306) access to the network fabric 302, and can connect the leaf switches 312 to each other. In some embodiments, the leaf switches 312 can connect endpoint groups (EPGs) to the network fabric 302, internal networks (e.g., the L2 network 304), and/or any external networks (e.g., the L3 network 306). EPGs are groupings of applications, or application components, and tiers for implementing forwarding and policy logic. EPGs can allow for separation of network policy, security, and forwarding from addressing by using logical application boundaries. EPGs can be used in the network environment 300 for mapping applications in the network. For example, EPGs can comprise a grouping of endpoints in the network indicating connectivity and policy for applications.

As discussed, the servers 308 can connect to the network fabric 302 via the leaf switches 312. For example, the servers 308 a and 308 b can connect directly to the leaf switches 312 a and 312 b, which can connect the servers 308 a and 308 b to the network fabric 302 and/or any of the other leaf switches. The servers 308 c and 308 d can connect to the leaf switches 312 b and 312 c via the L2 network 304. The servers 308 c and 308 d and the L2 network 304 make up a local area network (LAN). LANs can connect nodes over dedicated private communications links located in the same general physical location, such as a building or campus.

The WAN 306 can connect to the leaf switches 312 d or 312 e via the L3 network 306. WANs can connect geographically dispersed nodes over long-distance communications links, such as common carrier telephone lines, optical light paths, synchronous optical networks (SONET), or synchronous digital hierarchy (SDH) links. LANs and WANs can include L2 and/or L3 networks and endpoints.

The Internet is an example of a WAN that connects disparate networks throughout the world, providing global communication between nodes on various networks. The nodes typically communicate over the network by exchanging discrete frames or packets of data according to predefined protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP). In this context, a protocol can refer to a set of rules defining how the nodes interact with each other. Computer networks may be further interconnected by an intermediate network node, such as a router, to extend the effective size of each network. The endpoints 308 can include any communication device or component, such as a computer, server, blade, hypervisor, virtual machine, container, process (e.g., running on a virtual machine), switch, router, gateway, host, device, external network, etc.

In some embodiments, the network environment 300 also includes a network controller running on the host 308 a. The network controller is implemented using the Application Policy Infrastructure Controller (APIC™) from Cisco®. The APIC™ provides a centralized point of automation and management, policy programming, application deployment, and health monitoring for the fabric 302. In some embodiments, the APIC™ is operated as a replicated synchronized clustered controller. In other embodiments, other configurations or software-defined networking (SDN) platforms can be utilized for managing the fabric 302.

In some embodiments, a physical server 308 may have instantiated thereon a hypervisor 316 for creating and running one or more virtual switches (not shown) and one or more virtual machines 318, as shown for the host 308 b. In other embodiments, physical servers may run a shared kernel for hosting containers. In yet other embodiments, the physical server 308 can run other software for supporting other virtual partitioning approaches. Networks in accordance with various embodiments may include any number of physical servers hosting any number of virtual machines, containers, or other virtual partitions. Hosts may also comprise blade/physical servers without virtual machines, containers, or other virtual partitions, such as the servers 308 a, 308 c, 308 d, and 308 e.

The network environment 300 can also integrate a network traffic monitoring system, such as the network traffic monitoring system 200 shown in FIG. 2. For example, the network traffic monitoring system of FIG. 3 includes sensors 320 a, 320 b, 320 c, and 320 d (collectively, “320”), collectors 322, and an analytics engine, such as the analytics engine 210 of FIG. 2, executing on the server 308 e. The analytics engine 308 e can receive and process network traffic data collected by the collectors 322 and detected by the sensors 320 placed on nodes located throughout the network environment 300. Although the analytics engine 308 e is shown to be a standalone network appliance in FIG. 3, it will be appreciated that the analytics engine 308 e can also be implemented as a virtual partition (e.g., VM or container) that can be distributed onto a host or cluster of hosts, software as a service (SaaS), or other suitable method of distribution. In some embodiments, the sensors 320 run on the leaf switches 312 (e.g., the sensor 320 a), the hosts 308 (e.g., the sensor 320 b), the hypervisor 316 (e.g., the sensor 320 c), and the VMs 318 (e.g., the sensor 320 d). In other embodiments, the sensors 320 can also run on the spine switches 310, virtual switches, service appliances (e.g., firewall, deep packet inspector, traffic monitor, load balancer, etc.) and in between network elements. In some embodiments, sensors 320 can be located at each (or nearly every) network component to capture granular packet statistics and data at each hop of data transmission. In other embodiments, the sensors 320 may not be installed in all components or portions of the network (e.g., shared hosting environment in which customers have exclusive control of some virtual machines).

As shown in FIG. 3, a host may include multiple sensors 320 running on the host (e.g., the host sensor 320 b) and various components of the host (e.g., the hypervisor sensor 320 c and the VM sensor 320 d) so that all (or substantially all) packets traversing the network environment 300 may be monitored. For example, if one of the VMs 318 running on the host 308 b receives a first packet from the WAN 306, the first packet may pass through the border leaf switch 312 d, the spine switch 310 b, the leaf switch 312 b, the host 308 b, the hypervisor 316, and the VM. Since all or nearly all of these components contain a respective sensor, the first packet will likely be identified and reported to one of the collectors 322. As another example, if a second packet is transmitted from one of the VMs 318 running on the host 308 b to the host 308 d, sensors installed along the data path, such as at the VM 318, the hypervisor 316, the host 308 b, the leaf switch 312 b, and the host 308 d will likely result in capture of metadata from the second packet.

FIG. 4 illustrates an example of a data pipeline 400 for determining clusters in an application dependency map in accordance with an example embodiment. In some embodiments, the data pipeline 400 can be directed by a network traffic monitoring system, such as the network traffic monitoring system 200 of FIG. 2; an analytics engine, such as the analytics engine 210 of FIG. 2; an application dependency mapping module, such as the ADM module 240 of FIG. 2; or other network service or network appliance. The data pipeline 400 includes a data collection stage 402 in which network traffic data and corresponding data (e.g., host data, process data, user data, etc.) are captured by sensors (e.g., the sensors 204 of FIG. 2) located throughout the network. As discussed, the data can be captured from multiple perspectives to provide a comprehensive view of the network. The data collected may also include other types of information, such as tenant information, virtual partition information, out-of-band information, third party information, and other relevant information. In some embodiments, the flow data and associated data can be aggregated and summarized daily or according to another suitable increment of time, and flow vectors, process vectors, host vectors, and other feature vectors can be calculated during the data collection stage 402. This can substantially reduce processing during an ADM run.

The data pipeline 400 also includes an ADM input data stage 404 in which a network or security administrator or other authorized user may configure an ADM run by selecting the date range of the flow data and associated data to analyze, and those nodes for which the administrator wants application dependency maps and/or cluster information. In some embodiments, the administrator can also input side information, such as server load balance, route tags, and previously identified clusters during the ADM input data stage 404. In other embodiments, the side information can be automatically pulled or another network element can push the side information for the ADM run.

The next stage of the data pipeline 400 is pre-processing 406. During the pre-processing stage 406, nodes of the network are partitioned into selected node and dependency node subnets. Selected nodes are those nodes for which the user requests application dependency maps and cluster information. Dependency nodes are those nodes that are not explicitly selected by the users for an ADM run but are nodes that communicate with the selected nodes. To obtain the partitioning information, edges of an application dependency map (i.e., flow data) and unprocessed feature vectors can be analyzed.

Other tasks can also be performed during the pre-processing stage 406, including identifying dependencies of the selected nodes and the dependency nodes; replacing the dependency nodes with tags based on the dependency nodes' subnet names; extracting feature vectors for the selected nodes, such as by aggregating daily vectors across multiple days, calculating term frequency-inverse document frequency (tf-idf), and normalizing the vectors (e.g., €₂ normalization); and identifying existing clusters.

After pre-processing, the data pipeline 400 may proceed to a clustering stage 408. In the clustering stage 408, various machine learning techniques can be implemented to analyze feature vectors within a single domain or across different domains to determine the optimal clustering given a set of input nodes. Machine learning is an area of computer science in which the goal is to develop models using example observations (i.e., training data), that can be used to make predictions on new observations. The models or logic are not based on theory but are empirically based or data-driven.

Machine learning can be categorized as supervised or unsupervised. In supervised learning, the training data examples contain labels for the outcome variable of interest. There are example inputs and the values of the outcome variable of interest are known in the training data. The goal of supervised learning is to learn a method for mapping inputs to the outcome of interest. The supervised models then make predictions about the values of the outcome variable for new observations. Supervised learning methods include boosting, neural networks, and random forests, among others.

Boosting is a machine learning algorithm which finds a highly accurate hypothesis (e.g., low error rate) from a combination of many “weak” hypotheses (e.g., substantial error rate). Given a data set comprising examples within a class and not within the class and weights based on the difficulty of classifying an example and a weak set of classifiers, boosting generates and calls a new weak classifier in each of a series of rounds. For each call, the distribution of weights is updated that indicates the importance of examples in the data set for the classification. On each round, the weights of each incorrectly classified example are increased, and the weights of each correctly classified example is decreased so the new classifier focuses on the difficult examples (i.e., those examples have not been correctly classified).

Neural networks are inspired by biological neural networks and consist of an interconnected group of functions or classifiers that process information using a connectionist approach. Neural networks change their structure during training, such as by merging overlapping detections within one network and training an arbitration network to combine the results from different networks. Examples of neural network-based approaches include the multilayer neural network, the auto associative neural network, the probabilistic decision-based neural network (PDBNN), and the sparse network of winnows (SNOW).

A random forest is a machine learning algorithm that relies on a combination of decision trees in which each tree depends on the values of a random vector sampled independently and with the same distribution for all trees in the forest. A random forest can be trained for some number of trees ‘T’ by sampling ‘N’ cases of the training data at random with replacement to create a subset of the training data. At each node, a number ‘m’ of the features are selected at random from the set of all features. The feature that provides the best split is used to do a binary split on that node. At the next node, another number ‘m’ of the features are selected at random and the process is repeated.

In unsupervised learning, there are example inputs, however, no outcome values. The goal of unsupervised learning can be to find patterns in the data or predict a desired outcome. Unsupervised learning methods include principle component analysis (PCA), expectation-maximization (EM), and clustering, among others.

PCA is a machine learning algorithm that uses an orthogonal transformation to convert a set of observations of possibly correlated variables into a set of values of linearly uncorrelated variables called principal components. The number of principal components is less than or equal to the number of original variables. This transformation is defined in such a way that the first principal component has the largest possible variance (i.e., the principal component accounts for as much of the variability in the data as possible), and each succeeding component in turn has the highest variance possible under the constraint that it is orthogonal to the preceding components. The resulting vectors are an uncorrelated orthogonal basis set.

Clustering is a process that groups a set of objects into the same group (i.e., cluster) when the objects are more similar, less distant, denser, or otherwise share more attributes with respect to each other than to those in other groups. An example of clustering is the k-means algorithm in which a number of n nodes are partitioned into k clusters such that each node belongs to the cluster with the nearest mean. The algorithm proceeds by alternating steps, assignment and update. During assignment, each node is assigned to a cluster whose mean yields the least within-cluster sum of squares (WCSS) (i.e., the nearest mean). During update, the new means is calculated to be the centroids of the nodes in the new clusters. Convergence is achieved when the assignments no longer change. In some embodiments, k can be determined based on MDL as discussed elsewhere herein.

The k-means algorithm is an example of partition clustering. Other approaches for clustering include hierarchical clustering (e.g., agglomerative and divisive methods), density-based clustering (e.g., EM or DBSCAN), model-based clustering (e.g., decision trees or neural networks), grid-based clustering (e.g., fuzzy or evolutionary methods), among other categories.

EM is an iterative process for finding the maximum likelihood or maximum a posteriori estimates of parameters in a statistical model, where the model depends on unobserved latent variables. The EM iteration alternates between performing an expectation (E) step, which creates a function for the expectation of the log-likelihood evaluated using the current estimate for the parameters, and a maximization (M) step, which computes parameters maximizing the expected log-likelihood found during the E step. These parameter-estimates are then used to determine the distribution of the latent variables in the next E step.

In some embodiments, the clustering stage 408 can include a determination of the optimal number of clusters using the minimum description length (MDL) principle. As discussed, the MDL principle is that the best model or hypothesis for a given set of data is the one that leads to best compression of the data (i.e., minimizes the total length of the hypothesis plus the description of the exceptions to the hypothesis). MDL can be attractive to implement because MDL balances how well the model or theory fits with respect to observations and the complexity or richness of the model or theory, MDL techniques automatically and inherently avoid overfitting and can be used to determine both the parameters and the number of parameters of the model or theory, MDL processes do not require a ground truth model, and MDL methods provide good predictive performance on unobserved data.

In some embodiments, a suitable network component (e.g., network traffic monitoring system, analytics engine, ADM module, etc.), or generally, a network, may implement instructions, which can be similar to the example pseudo code recited in Table 1, for determining the optimal number of clusters. It should be understood that, for any process discussed herein, there can be additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel, within the scope of the various embodiments unless otherwise stated. To begin, the network can generate a graph using network traffic and corresponding data collected during a specified period of time. Nodes of the graph can include source endpoints (i.e., clients), destination endpoints (i.e., servers), and destination ports (i.e., server ports). Edges of the graph may correspond to observed traffic from the source endpoints to the destination endpoints at the destination ports. In some embodiments, the edges of the graph can be associated with values or weights reflecting an absolute number of flows or a relative number of flows of the edge relative to other edges. For purposes of simplicity and clarity, the graph representation of flow data is limited to the source network address, destination network address, and destination port in this example. However, it should be appreciated that other embodiments may additionally or alternatively use other nodes based on other features or attributes of the network domain (e.g., source port, number of packets for a flow, number of bytes for a flow, etc.) and/or features or attributes of the process domain (e.g., process name, parent process, process owner, etc.) and/or features or attributes of other domains (e.g., host domain, virtual partition domain, user domain, etc.).

To determine the optimal number of clusters ‘k’ for the network, the network can evaluate an MDL score for each potential value of ‘k,’ where ‘k’ can be between 1 (i.e., all of the nodes of the network form a single cluster) and the number of nodes in the graph ‘n’ (i.e., each node forms its own cluster). The MDL score for a particular clustering can be the based on description lengths of observed flows. In this example, the MDL score is the sum of the description lengths for each source cluster—destination cluster—destination port combinations for a particular clustering. As discussed, in other embodiments, the description lengths can be represented additionally or alternatively by other nodes corresponding to other features and attributes of the same domain (i.e., network domain) and/or features of other domains (e.g., process domain, host domain, virtual partition domain, user domain, etc.). In other embodiments, the MDL score can also represent edges as various empirical values or weights. For example, in an embodiment, an MDL score can factor in the absolute number of flows or the relative number of flows of an edge such as by associating the each edge with particular values or weights depending on the number of flows observed for each edge.

In this example, the description length is a function of the minimum between observed graph edges and unobserved graph edges+1, where observed graph edges can be calculated as the product of the number of unique source nodes and destination nodes and unobserved graph edges can be a difference of the number of observed edges and the product of the number of nodes in each source cluster and the number of nodes in each destination cluster. In this example, a better clustering corresponds to a lower MDL score. Thus, the optimal number of clusters ‘k’ is the clustering with the minimum MDL score.

In other embodiments, the description length and the interpretation of the MDL scores depend on the features selected for representing a flow, the domains selected for representing a flow, how feature values are represented, and how the features are combined within a domain and across domains, among numerous other factors. The appropriate description length and MDL score interpretation will be apparent to those of ordinary skill in the art when practicing the various embodiments.

TABLE 1 Example pseudo code for determining optimal number of clusters in accordance with an embodiment  1: initialize G // G is graph with client nodes, server nodes, and server ports nodes and edges from client nodes to server nodes to server port nodes if data flow is observed for that combination, initialize G by generating the graph  2: initialize k // k is optimum number of clusters for a network, initialize k by setting default value for k (e.g., number of nodes n/3 in the graph G)  3: initialize s_(c) // s_(c) is MDL score for current optimal clustering, initialize s_(c) by setting default value for s_(c) (e.g., MDL score for max number of clusters, i.e., number of nodes n in the graph G)  4: for (i = 1; i < n − 1; i++)  5: initialize s_(i) = 0 // s_(i) is the MDL score for a clustering c_(i)  6: for each src cluster-dest cluster-port combination in cluster c_(i)  7: set m = number of observed edges, where an edge is a flow from src node (i.e., client) to dest node (i.e., server) at dest node port (i.e., server port)  8: set n = the number of unobserved edges  9: compute d = min(m, 1 + n) // d is the description length for a src cluster-dest cluster-port combination 10: s_(i) += d // MDL score for clustering c_(i) is sum of descriptions lengths across all src cluster-dest cluster-port combinations 11: if (s_(i) < s_(c)) 12: s_(c) = s_(i) 13: k = i // optimal number of clusters is minimum MDL score

FIG. 5 illustrates an example of a graph 500 that can be used to calculate an MDL score for a particular clustering in accordance with an embodiment. It will be appreciated that the graph 500 is only provided herein for purposes of explaining how to compute the MDL score computed from the graph 500 but a graph corresponding to the traffic flow of an actual network would unlikely be limited to the number of nodes and edges of the graph 500. For example, the number of nodes and edges of a small enterprise network may be in the hundreds or thousands or much greater if, for instance, the network provides support for the Internet of Things (IoT) applications. Further, most if not all the edges of such a graph are likely to be bidirectional due to the handshaking that most network protocols require.

The graph 500 includes nodes 502 a, 502 b, . . . 502 h (collectively, “502”). Each node can represent an endpoint (e.g., physical object capable of network communication, virtual partition, network device, etc.), an EPG (e.g., subnet, network, or other collection of endpoints), or a combination thereof depending on the specified granularity of the application dependency map. The nodes 502 can be connected to each other via edges 504 af, 504 ag, . . . , 504 nn (collectively, “504”). Each edge can represent a unidirectional flow between a source node and a destination node, a bidirectional flow, a direct physical link, or a virtual link. In some embodiments, each edge may also be associated with network statistics related to its flow(s), such as the total number of packets, the total number of bytes, and/or total number of flows, among other statistics. As discussed, these network statistics can be used to weight each edge for determining the MDL score of a particular clustering. In this example, the edges 504 represent unidirectional flows that travel in the direction indicated by the arrows.

The possible range of the number clusters of the graph 500 is from 1, wherein all of the nodes form a single cluster, to 8, the total number of nodes ‘n’ in the graph, wherein each node forms a separate cluster. However, the range of the number of clusters for most networks will fall within a smaller range between the maximum. In an embodiment, the initial value for determining the optimal number of clusters ‘k’ for the graph 500 can be set to ‘n/3’ or the total number of nodes of the graph divided by three. As would be understood by one of ordinary skill, the more that is known about a network, the more the range of the possible number of clusters ‘k’ can be limited to reduce the amount of time and processing needed by eliminating possible values for ‘k’ that are not applicable for the network. For example, if the network is known to have a number of three-tier applications ‘a,’ then the lower bound for the possible number of clusters ‘k’ can be set to ‘3×a’ because there are at least ‘3×a’ different clusters for each tier of the number of applications ‘a’ and the upper bound for the possible number of clusters ‘k’ can be set to ‘n−a’ because there can be no more than ‘n−a’ clusters in the network.

To calculate the optimal number of clusters ‘k’ for the graph 500, the initial value T can be set to a particular value, such as 1 or other suitable default value. For purposes of conciseness, T is set to 4. Although the MDL score for each possible clustering for ‘i=4’ would be computed to determine the minimum MDL score for ‘i=4,’ for brevity, the clustering of {A, B, C, D, E}; {F}; {G}; and {H} can be selected. With this configuration, traffic corresponds to the following patterns: {A, B, C, D, E} to {F}; {A, B, C, D, E} to {G}; and {A, B, C, D, E} to {H}.

For {A, B, C, D, E} to {F}, the graph 500 includes 2 observed edges, 504 af and 504 bf, and three unobserved edges, 504 cf, 504 df, and 504 ef. The description length for this traffic pattern is the minimum of the observed edges and unobserved edges+1, i.e., min(2,3+1) or 2.

For {A, B, C, D, E} to {G}, the graph 500 includes 2 observed edges, 504 cg and 504 dg, and three unobserved edges, 504 ag, 504 bg, and 504 eg, and the description length for this traffic pattern is min(2,3+1) or 2.

For {A, B, C, D, E} to {H}, the graph 500 includes 1 observed edge, 504 eh, and 4 unobserved edges, 504 ah, 504 bh, 504 ch, 504 dh. The description length for this pattern is min(1,4+1) or 1.

The MDL score for this particular clustering of ‘i=4,’ is the sum of the description lengths, i.e., 2+2+1 or 5. If this clustering is the lowest MDL score, then the optimal number of clusters ‘k’ is 4. This process is repeated for each value of T until the number of clusters ‘n’ in the graph 500 or other suitable maximum number selected based on predetermined information known about the network. However, for purposes of simplicity and conciseness, the next value of ‘i’ can be set to 6 for the clusters {A, B}; {C, D}; {E}; {F}; {G}; and {H}. With this clustering, the possible permutations for traffic can include the following patterns: {A, B} to {F}, {C, D} to {G}, and {E} to {H}; {A, B} to {F}, {C, D} to {H}, and {E} to {G}; {A, B} to {G}, {C, D} to {F}, and {E} to {H}; {A, B} to {G}, {C, D} to {H}, and {E} to {F}; {A,B} to {H}, {C, D} to {F}, and {E} to {G}; {A, B} to {H}, {C, D} to {G}, and {E} to {F}.

For the first pattern, the graph 500 includes 3 observed edges and 0 unobserved edges such that the description length is min(3,0+1) or 1. For the second, third, and sixth patterns, the number of observed edges is 1 and the number of unobserved edges is 2 such that the description length is min(1,2+1) or 1 for these patterns. For the fourth and fifth, the number of observed edges is 0 and the number of unobserved edges is 3 and the description lengths for these patterns is min(0, 3+1) or 0. The MDL score for this particular clustering of ‘i=6’ is the sum of the description lengths of 1+1+1+0+0+1 or 4. Thus, this particular clustering of ‘i=6’ would be selected over the example of the first clustering of ‘i=4,” and the optimal number of clusters ‘k’ would be set to 6, and the process would be repeated for every other possible clustering of ‘i=6,’ and then for every value of T until the number of nodes in the graph or other maximum.

As discussed, some networks may be made up of several partitions. For example, multiple partitions in a network can arise from routing information or subnet masking. As another example, some public cloud providers may partition their network according to regions zones. Under these circumstances or similar situations, clusters may not span the multiple partitions (i.e., a cluster may not include endpoints that are located in different partitions). Thus, the optimal clustering may vary from one partition to another in networks with multiple partitions. In some embodiments, the MDL principle can be used to improve the number of clusters for each individual partition by using a randomized local search algorithm based upon local searches.

In some embodiments, a multi-partitioned network (or a suitable component of the network) may implement instructions, which can be similar to the example pseudo code recited in Table 2, for determining the optimal number of clusters k_(i) for each partition p_(i). The network can begin by selecting a default value for each partition ‘p_(i)’ in the network. In an embodiment, the default value of ‘k_(i)’ can be the total number of nodes in the network ‘n’ divided by 3. The MDL score can be computed for the current state (i.e., current p_(i), current k_(i)), and this step can be repeated for ‘n’ iterations or until the change in energy ‘Δ’ is smaller than a delta threshold ‘t,’ wherein the set of partitions ‘P’ is randomized for each iteration. In this example, the MDL score for a particular partition ‘p_(i)’ and potential optimal number of clusters T can be computed similarly to the approach discussed above with respect to Table 1. In this example, the optimal number of clusters k_(i) for a particular partition p_(i) can be based on the highest energy state (e.g., lowest MDL score) evaluated for each k_(i) for the partition p_(i). It will be appreciated that appreciated that various embodiments may employ other description length representations and MDL score interpretations depending on selected features, domains, value representations, and combinations, among other factors.

TABLE 2 Pseudo code for determining optimal number of nodes k in each partition p in accordance with an embodiment  1: initialize k_(i) // k_(i) is optimal number of nodes in partition p_(i), initialize k_(i) by selecting default value (e.g., total number of nodes in network n / 3)  2: initialize P // P is set of partitions in network  3: initialize partition p // select default partition (e.g., first(P))  4: initialize energy E₀// E₀ is current energy, select default energy (e.g., MDL(p, k) which is the MDL score for partition p for all clusterings based on k)  5: initialize Δ // Δ is change in energy, select default change in energy (e.g., ∞)  6: for (i=k; i ≤ n && Δ > delta threshold t; i++)  7: set P = random order of partitions in P  8: while (P not null)  9: set p = pop(P) 10: set new energy E₁ = MDL(p, i) // compute MDL for current partition p for all clusterings based on i) 11: set Δ = | E₁ − E₀ | 12: if E₁ < E₀ // new energy E₁ is lower than current energy E0, i.e., lower MDL score and better clustering 13: set E₀ = E₁ 14: set k = i // pick best k, i.e., highest energy for each partition

In some embodiments, the clustering stage 408 can also include a determination of the optimal clustering given the optimal number of clusters determined via MDL theory. For example, network nodes can be evaluated using machine learning to identify an optimal clustering based on similarity amongst the network nodes. After clusters are identified, the data pipeline 400 can include a post-processing stage 410. The post-processing stage 410 can include tasks such as naming or labeling clusters, which may be automatic or user-specified; identifying cluster edges; and validating the clusters, such as by calculating silhouette scores. Silhouette scoring is a method of interpretation and validation of consistency within clusters of data. A silhouette score is a measure of how similar an object is to its own cluster compared to other clusters, which can range from −1 to 1, where a high value indicates that the node is well matched to its own cluster and badly matched to neighboring clusters. If most nodes have a high silhouette score, then the clustering maybe accurate. If many nodes have a low or negative silhouette score, then the clustering may have too many or too few clusters. The silhouette score can be calculated with any similarity or distance metric, such as the Euclidean distance or the Manhattan distance.

The end of the data pipeline 400 is a presentation stage 412 in which clustering data can be meaningfully and intuitively displayed to the user. In some embodiments, a user interface of the presentation stage 412 may allow the user to view statistics on clusters (e.g., number of nodes, edges, clusters, summaries of changes in clustering from the last ADM run, etc.) and detailed information for each cluster (e.g., nodes, server ports, and client ports, etc.). In some embodiments, the user interface may also allow the user to edit clusters (e.g., add or modify names and descriptions of clusters, move nodes from one cluster to another, approve an automatically determined cluster). In some embodiments, the user may operate the user interface to create application profiles, or to perform ADM re-runs.

In some embodiments, a network (or a suitable component of the network) can be utilized to generate policies and simulate enforcement based on one or more application dependency mappings, such as generated using the various embodiments disclosed herein. For example, the network can receive one or more application dependency mappings, and automatically determine policies for the network. The policies can be based on whitelist rules or blacklist rules. As an example of whitelist rule generation, suppose there is an edge of an application dependency mapping between a first endpoint or EPG E1 and a second endpoint or EPG E2. Permissible traffic flows on a set of ports of E1 to one or more ports of E2. A policy can be defined to reflect the permissible traffic from the set of ports of E1 to the one or more ports of E2.

In some embodiments, the network can be used to validate that changes to policy will not result in network misconfiguration and vulnerability to attacks. That is, the network can provide what if analysis, i.e., analyzing what would happen to network traffic upon adding one or more new policies, removing one or more existing policies, or changing membership of one or more EPGs (e.g., adding one or more new endpoints to an EPG, removing one or more endpoints from an EPG, or moving one or more endpoints from one EPG to another). In some embodiments, the network may utilize historical ground truth flows for simulating network traffic based on what if experiments. That is, the network may apply the addition or removal of policies and/or changes to EPGs to a simulated network environment that mirrors the actual network to evaluate the effects of the addition or removal of policies and/or EPG changes. The network can determine whether the policy changes break or misconfigure networking operations of any applications in the simulated network environment or allow any attacks to the simulated network environment that were previously thwarted by the actual network with the original set of policies. The network can also determine whether the policy changes correct misconfigurations and prevent attacks that occurred in the actual network. In some embodiments, the network can evaluate real time flows in a simulated network environment configured to operate with an experimental policy set or experimental set of EPGs to understand how changes to particular policies or EPGs affect network traffic in the actual network.

It should be understood that the data pipeline 400 is only an example and that stages may be added, combined, removed, or modified without departing from the scope of the various embodiments.

FIG. 6 illustrates an example of a process 600 for determining an optimal number of clusters for automated application dependency mapping in accordance with an embodiment. The process 600 can be performed by a network, and particularly, a network traffic monitoring system (e.g., the network traffic monitoring system 200 of FIG. 2), an analytics engine (e.g., the analytics engine 210 of FIG. 2), a network controller (e.g., the network controller 218 of FIG. 2), an ADM module (e.g., the ADM module 240 of FIG. 2), a network operating system, a virtualization manager, a network virtualization manager, or similar system.

In the embodiment of FIG. 6, the process 600 can begin at step 602 in which the network captures data for each node of the network (or at least for a monitored set of nodes) across multiple domains, such as a network domain, host domain, process domain, and/or user domain. In some embodiments, virtualization information, network topology information, and application information (e.g., configuration information, previously generated application dependency maps, application policies, etc.) may also be collected. In some embodiments, out-of-band data (e.g., power level, temperature, and physical location) and third party data (e.g., CMDB or CMS as a service, Whois, geocoordinates, etc.) can also be collected.

As discussed, a sensor network can collect the captured data from multiple perspectives to provide a comprehensive view of network behavior. The sensor network may include sensors at multiple nodes of a data path (e.g., network devices, physical servers) and within multiple partitions of a node (e.g., hypervisor, shared kernel, VM, container, etc.).

After collection of the multi-domain data, the process 600 may continue on to step 604, in which the network determines a communication graph from the data collected in step 602. The nodes of the graph can include source endpoints, destination endpoints, and destination ports identified in the captured data. The edges of the graph may correspond to observed traffic from the source endpoints to the destination endpoints at the destination ports.

At step 606, the network can determine an MDL score for a potential clustering. The MDL score for an individual clustering can be based on a sum of description length values for each cluster combination of the individual clustering (e.g., source cluster-destination cluster-port combination). The description length value for an individual cluster combination can be based on a number of observed edges of the graph and unobserved edges of the graph corresponding to the individual cluster combination.

After the network determines the MDL score for the potential clustering, the process 600 may proceed to decision point 608. At decision point 608, the network can determined whether the MDL score for the potential clustering is the minimum MDL score for all potential clusterings. If the currently analyzed clustering is not associated with the minimum MDL score, the process 600 may return to step 606 to analyze another potential clustering.

If the currently analyzed clustering is associated with the minimum MDL score, the process 600 may conclude at step 610 in which the optimum number of clusters for the network can be determined based on the number of clusters corresponding to the clustering associated with the minimum MDL score.

In some embodiments, a network may comprise multiple partitions in which clusters may not span the multiple partitions. The optimal clustering may vary from one partition to another in such networks. In some embodiments, the MDL principle can be used to improve the number of clusters for each individual partition by using a randomized local search algorithm based upon local searches. The network can determine an MDL score for each potential number of clusters for each of the multiple partitions (or at least until a change in energy is below a threshold change), and the determined number of clusters for each of the multiple partitions can correspond to the highest energy state (e.g., lowest MDL score) for a particular partition.

In some embodiments, an application dependency mapping determined by the network can be used to automatically generate policies, such as those based on whitelist rules. In some embodiments, the generated set of policies can be enforced in a simulated environment mirroring the network to determine the effects of changing a previous set of policies to the generated set of policies.

FIG. 7A and FIG. 7B illustrate systems in accordance with various embodiments. The more appropriate system will be apparent to those of ordinary skill in the art when practicing the various embodiments. Persons of ordinary skill in the art will also readily appreciate that other systems are possible.

FIG. 7A illustrates an example architecture for a conventional bus computing system 700 wherein the components of the system are in electrical communication with each other using a bus 705. The computing system 700 can include a processing unit (CPU or processor) 710 and a system bus 705 that may couple various system components including the system memory 715, such as read only memory (ROM) in a storage device 770 and random access memory (RAM) 775, to the processor 710. The computing system 700 can include a cache 712 of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 710. The computing system 700 can copy data from the memory 715 and/or the storage device 730 to the cache 712 for quick access by the processor 710. In this way, the cache 712 can provide a performance boost that avoids processor delays while waiting for data. These and other modules can control or be configured to control the processor 710 to perform various actions. Other system memory 715 may be available for use as well. The memory 715 can include multiple different types of memory with different performance characteristics. The processor 710 can include any general purpose processor and a hardware module or software module, such as module 1 732, module 2 734, and module 3 736 stored in storage device 730, configured to control the processor 710 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 710 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing system 700, an input device 745 can represent any number of input mechanisms, such as a microphone for speech, a touch-protected screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 735 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing system 700. The communications interface 740 can govern and manage the user input and system output. There may be no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 730 can be a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 725, read only memory (ROM) 720, and hybrids thereof.

The storage device 730 can include software modules 732, 734, 736 for controlling the processor 710. Other hardware or software modules are contemplated. The storage device 730 can be connected to the system bus 705. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 710, bus 705, output device 735, and so forth, to carry out the function.

FIG. 7B illustrates an example architecture for a conventional chipset computing system 750 that can be used in accordance with an embodiment. The computing system 750 can include a processor 755, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. The processor 755 can communicate with a chipset 760 that can control input to and output from the processor 755. In this example, the chipset 760 can output information to an output device 765, such as a display, and can read and write information to storage device 770, which can include magnetic media, and solid state media, for example. The chipset 760 can also read data from and write data to RAM 775. A bridge 780 for interfacing with a variety of user interface components 785 can be provided for interfacing with the chipset 760. The user interface components 785 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. Inputs to the computing system 750 can come from any of a variety of sources, machine generated and/or human generated.

The chipset 760 can also interface with one or more communication interfaces 790 that can have different physical interfaces. The communication interfaces 790 can include interfaces for wired and wireless LANs, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 755 analyzing data stored in the storage device 770 or the RAM 775. Further, the computing system 700 can receive inputs from a user via the user interface components 785 and execute appropriate functions, such as browsing functions by interpreting these inputs using the processor 755.

It will be appreciated that computing systems 700 and 750 can have more than one processor 710 and 755, respectively, or be part of a group or cluster of computing devices networked together to provide greater processing capability.

For clarity of explanation, in some instances the various embodiments may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. 

The invention claimed is:
 1. A method comprising: capturing network flow data using sensors executing on servers of a data center network and sensors executing on networking devices connected to the servers; determining a graph including nodes, representing at least the servers, and edges, between pairs of the nodes of the graph indicating the network flow data includes one or more observed flows between pairs of the servers represented by the pairs of the nodes; determining a dependency map, including representations of clusters of the servers and representations of dependencies between the clusters, based on the graph; determining the confidence level of identifying a first cluster based on a similarity measure between one or more first servers of the first cluster relative to similarity measures between the one or more first servers and one or more second servers of one or more second clusters of the dependency map; identifying one or more dependencies between the first cluster and one or more second clusters of the dependency map; determining one or more whitelist policies based on the one or more dependencies; and displaying a first representation of the first cluster of the dependency map and information indicating a confidence level of identifying the first cluster.
 2. The method of claim 1, further comprising: capturing the network flow data using a first sensor executed by a first virtual machine provisioned on a first server of the data center network and a second sensor executed by a second virtual machine provisioned on the first server.
 3. The method of claim 1, further comprising: capturing the network flow data using a first sensor executed by a first container provisioned on a first server of the data center network and a second sensor executed by a second sensor provisioned on the first server.
 4. The method of claim 1, further comprising: determining unobserved edges between pairs of the nodes of the graph indicating the network flow data excludes any observed flows between pairs of servers represented by the pairs of the nodes; determining multiple clusterings of the servers of the data center network such that each clustering includes at least one different cluster of the servers; for each clustering of the multiple clusterings, determining a description length of each cluster of the clustering based on a number of the edges of the graph from the cluster to other clusters of the clustering and a number of the unobserved edges of the graph from the cluster to other clusters of the clustering; and determining an aggregate description length of the clustering based on the description length of each cluster of the clustering; determining a first clustering among the multiple clusterings having a minimum aggregate description length; and determining a number of the clusters of the dependency map based on a number of clusters of the first clustering.
 5. The method of claim 1, further comprising: determining weights for the edges between the pairs of the nodes of the graph based on a number of the observed flows between the pairs of the servers represented by the pairs of the nodes; and determining a number of the clusters of the dependency map based on the weights.
 6. The method of claim 1, wherein the graph includes a first node representing a first server of the data center network and a first port of the first server and a second node representing the first server and a second port of the first server.
 7. The method of claim 1, wherein the graph includes a first node representing a first server of the data center network and at least one of a first user, a first process, or a first tenant associated with one or more first observed flows to or from the first server and a second node representing the first server and at least one of a second user, a second process, or a second tenant associated with one or more second observed flows to or from the first server.
 8. The method of claim 1, further comprising: enforcing the one or more whitelist policies within a simulated environment corresponding to the data center network using at least one of historical network flow data or real time network flow data.
 9. The method of claim 1, further comprising: capturing at least one of process data, user data, virtualization data, or tenant data using the sensors.
 10. The method of claim 9, further comprising: determining the clusters based on at least one of the process data, the user data, the virtualization data, or the tenant data.
 11. A system comprising: one or more processors; and memory including instructions that, when executed by the one or more processors, cause the system to: capture network flow data using sensors executing on servers of a data center network and sensors executing on networking devices connected to the servers; determine a graph including nodes, representing at least the servers, and edges, between pairs of the nodes of the graph indicating the network flow data includes one or more observed flows between pairs of the servers represented by the pairs of the nodes; determine a dependency map, including representations of clusters of the servers and representations of dependencies between the clusters, based on the graph; determining the confidence level of identifying a first cluster based on a similarity measure between one or more first servers of the first cluster relative to similarity measures between the one or more first servers and one or more second servers of one or more second clusters of the dependency map; identifying one or more dependencies between the first cluster and one or more second clusters of the dependency map; determining one or more whitelist policies based on the one or more dependencies; and display a first representation of the first cluster of the dependency map and information indicating a confidence level of identifying the first cluster.
 12. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: capture at least one of process data, user data, virtualization data, or tenant data using the sensors; and determine the clusters based on at least one of the process data, the user data, the virtualization data, or the tenant data.
 13. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: determine unobserved edges between pairs of the nodes of the graph indicating the network flow data excludes any observed flows between pairs of servers represented by the pairs of the nodes; determine multiple clusterings of the servers of the data center network such that each clustering includes at least one different cluster of the servers; for each clustering of the multiple clusterings, determine a description length of each cluster of the clustering based on a number of the edges of the graph from the cluster to other clusters of the clustering and a number of the unobserved edges of the graph from the cluster to other clusters of the clustering; and determine an aggregate description length of the clustering based on the description length of each cluster of the clustering; determine a first clustering among the multiple clusterings having a minimum aggregate description length; and determine a number of the clusters of the dependency map based on a number of clusters of the first clustering.
 14. The system of claim 11, further comprising further instructions that, when executed by the one or more processors, further cause the system to: determine weights for the edges between the pairs of the nodes of the graph based on a number of the observed flows between the pairs of the servers represented by the pairs of the nodes; and determine a number of the clusters of the dependency map based on the weights.
 15. A non-transitory computer-readable medium having instructions that, upon being executed by one or more processors of a computing system, cause the computing system to: capture network flow data using sensors executing on servers of a data center network and sensors executing on networking devices connected to the servers; determine a graph including nodes, representing at least the servers, and edges, between pairs of the nodes indicating the network flow data includes one or more observed flows between pairs of the servers represented by the pairs of the nodes; generate a dependency map, including representations of clusters of the servers and representations of dependencies between the clusters, based on the graph; determining the confidence level of identifying a first cluster based on a similarity measure between one or more first servers of the first cluster relative to similarity measures between the one or more first servers and one or more second servers of one or more second clusters of the dependency map; identifying one or more dependencies between the first cluster and one or more second clusters of the dependency map; determining one or more whitelist policies based on the one or more dependencies; and display a first representation of the first cluster of the dependency map and information indicating a confidence level of identifying the first cluster.
 16. The non-transitory computer-readable medium of claim 15, further comprising further instructions that, when executed by the one or more processors, further cause the computing system to: enforce the one or more whitelist policies within a simulated environment corresponding to the data center network using at least one of historical ground truth network flow data or real time network flow data. 